Skip to content

fix: Case-insensitive globals matching (#684)#685

Merged
amilajack merged 1 commit intoamilajack:mainfrom
vsalomaki:fix/684-case-sensitivity-browser-globals
Mar 2, 2026
Merged

fix: Case-insensitive globals matching (#684)#685
amilajack merged 1 commit intoamilajack:mainfrom
vsalomaki:fix/684-case-sensitivity-browser-globals

Conversation

@vsalomaki
Copy link
Contributor

The case-insensitive matching of browser globals was way too broad as implemented in #681 and as reported in #684.

This PR narrows the scope of the object-name matching by first finding the name from the globals.browser case-sensitively.
If found from globals, then use case-insensitive comparison of the object-names. Otherwise use simple case-sensitive matching.

Add tests for both "valid" cases and "invalid" cases.

@vsalomaki vsalomaki force-pushed the fix/684-case-sensitivity-browser-globals branch from b576a07 to 7c79f50 Compare March 1, 2026 06:16
* Use case-insensitive objectname matching only for matching browserglobals
@vsalomaki vsalomaki force-pushed the fix/684-case-sensitivity-browser-globals branch from 7c79f50 to 0fdb0d1 Compare March 1, 2026 06:29
@amilajack amilajack merged commit 90ceb71 into amilajack:main Mar 2, 2026
5 checks passed
github-actions bot pushed a commit that referenced this pull request Mar 2, 2026
## [7.0.1](v7.0.0...v7.0.1) (2026-03-02)

### Bug Fixes

* Case-insensitive globals matching ([#684](#684)) ([#685](#685)) ([90ceb71](90ceb71))
@github-actions
Copy link

github-actions bot commented Mar 2, 2026

🎉 This PR is included in version 7.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants